Method and apparatus for base station self-configuration

ABSTRACT

Disclosed is method and apparatus for operation of a base station in wireless communications, including self-configuration of the base station for secure and authenticated communications with other base stations.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 11/964,596 filed on Dec. 26, 2007 which claims the benefit of U.S. Provisional Application No. 60/882,079 filed Dec. 27, 2006 which is incorporated by reference as if fully set forth.

FIELD OF INVENTION

The present application is related to wireless communications. More particularly, the present application is related to self-configuration and security features of a base station in wireless communications.

BACKGROUND

The 3rd Generation Partnership Project (3GPP) has initiated the Long Term Evolution (LTE) program to bring new technology, new network architecture, new configurations, new applications and new services to wireless cellular networks in order to provide improved spectral efficiency and faster user experiences.

While the demands continue for greater functionality, low maintenance LTE systems, particularly in terms of network deployment and runtime service optimization, are also in demand.

The UTRAN architecture used prior to LTE, the 3GPP Universal Mobile Telecommunication System (UMTS) system, is shown in FIG. 1. The core network 100 communicates with the UTRAN 110 that consists of multiple radio network systems (RNS) 120. Each RNS consists of a radio network controller (RNC) 130 and one or more Node-Bs 135. The configurations and operations of the deployed Node-Bs 135 are totally controlled by the RNC 130 with explicit commands over the Iub link 140. Iub 140 is an RNC-to-Node-B interface that has been previously defined. The configurations and service upgrade of Node-Bs depend on the RNC and other cell engineering and planning efforts. Prior to LTE, no connections existed between UTRAN Node-Bs 135 and no requirements existed for self configuration and optimization. No means of self configuration and no defined procedures operating among Node-Bs existed.

In the new LTE network system, as illustrated in FIG. 2, the E-UTRAN architecture has been changed. The former RNC node no longer exists. The evolved-Node-Bs (eNBs) 200, 205 perform the radio access network functionality for E-UTRAN 210, are linked directly with the Core Network (EPC) 220, and are linked together among themselves. In the E-UTRAN, the new eNBs 200, 205 assume the RAN configuration, operation and management control functions as well as the radio interface configurations and operations. Furthermore, each new eNB such as 200, now interacts directly with the LTE Core Network 220 over the S1 interface as well as interacting with neighboring eNBs 205 over the X2 interface 240 and X2 connection control (X2C) interface (not shown) for handling wireless transmit/receive unit (WTRU) mobility management tasks on behalf of the new E-UTRAN.

When a newly deployed eNB 200, 205 powers up, it performs self configuration tasks, including operations over the X2C interface to interact with neighboring operational eNBs. This initial interaction is used to gather information, to certify the eNB and to enable configurations and cooperation as the eNB readies itself to enter E-UTRAN operational mode for serving the WTRUs in its coverage area.

SUMMARY

The present application is related to operating procedures over a connection between base stations at a self-configuration phase.

Operations are disclosed for a self-configuring base station, and communication with connected neighboring base stations. A newly deployed base station performs the self configuration to associate itself with its neighboring operational base stations or cells. Security procedures are performed to protect the network from certain attacks.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an existing wireless communication system.

FIG. 2 is an illustration of an existing LTE architecture.

FIG. 3 is a flow diagram of one embodiment of a method of the present disclosure.

FIG. 4 is a flow diagram of a second embodiment of a method of the present disclosure.

FIG. 5 is a flow diagram of a third embodiment of a method of the present disclosure.

FIG. 6 shows a known type of security breach.

FIG. 7 is a flow diagram of a fourth embodiment of a method of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

When referred to hereafter, the terminology “wireless transmit/receive unit (WTRU)” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology “base station” includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment.

Although embodiments are described here in the context of LTE, they should be construed as examples and not limited to this particular wireless technology.

FIGS. 3-6 depict time sequences of events occurring in a self-configuring eNB, an eNB connected to (that is, “neighboring”) the self-configuring eNB, and an access gateway. The sequence begins at the top with time progressing downward. Events at the same horizontal level are occurring simultaneously.

Referring now to FIG. 3, when the self configuring eNB powers up, its S1 interface is preferably powered up first (step 305). The general internet protocol (IP) function or the eNB specific IP address resolution function obtains a unique IP address for the self configuring eNB over the S1 interface (step 300). The self-configuring eNB will then perform the eNB network authentication with its primary operator's serving access gateway (aGW) (step 310).

When the self-configuring eNB has succeeded with its network authentication, it then powers up and initializes (step 320) with its IP address, either configured or obtained through the S1 interface or the X2 interfaces, which connect the self-configuring eNB with other neighboring LTE eNBs.

As an optional early action, the eNB may then obtain the identities of its X2-connected neighboring eNBs, for example, their eNB-Id(s) and/or Cell-Id(s), public land mobile network (PLMN)-Id(s) and other non-confidential information such as current operating status (step 330). The eNB may then inform the serving aGW so that the eNB acquires the necessary network instructions and/or authorizations in connection with the X2-connected neighboring eNBs for authorized and permitted operations, such as WTRU handover or eNB measurement and report retrieval. Although this optional early action (step 330) is shown in FIG. 3 as a “handshake” it could also be a pair of request and response messages as shown in FIG. 7 or any other appropriate procedure. The neighboring eNBs to be contacted for such information are those that are pre-configured in the default neighboring eNBs list, such as those stored in the UMTS integrated circuit card (UICC) device.

This method for early action enables the network to maintain certain input or control over the inter-E-UTRAN operations in a multi-vendor/multi-operator environment. First, the process allows the eNB to gather accurate neighboring eNB information from those eNBs that respond in comparison with the pre-configured neighboring eNB list so that the eNB can inform the network/EPC about the new eNB and its connected neighbors and their actual operating status. Second, the eNB can obtain operational guides from the network regarding the policies of the X2C interface with the neighboring LTE eNBs, as the neighboring eNBs may or may not belong to the same network provider/operator. The eNB may also obtain other important operational information.

The one-way optional collection by the self-configuring eNB of its neighbor's non-confidential information does not include sensitive information retrieval. The collection of sensitive information by an eNB from its neighbors occurs at a later stage, when the inter-eNB authentication and security key associations have taken place.

After the initial data collection, the eNB will then send an E-UTRAN parameter request 340 over S1 with the information it obtained in the early X2C step disclosed above. Alternatively, the eNB will send the Request over the S1 if the early X2C action is not taken. In an E-UTRAN parameter response 350, the self-configuring eNB obtains needed operating parameters for the E-UTRAN, including parameters for inter-eNB authentication and security key agreement procedures over X2C, such as a universal eNB credential, a universal eNB shared secret key, inter-eNB security algorithm to be used and a universal eNB security keyset.

A need for authenticity, integrity and confidentiality protection on X2C has been previously documented. A light-weight authentication, defined herein as the inter-eNB authentication, and integrity and/or ciphering key agreement, defined herein as the security key association procedure, are disclosed below for LTE inter-eNB authentication and security key association between any pairs of eNBs, including between a self-configuring eNB and its already deployed operational neighboring eNBs.

Note that the inter-eNB authentication procedure in the eNB self configuration is required to ascertain the authenticity of the eNB pair at the node level. Authentication performed below without the node level control and the node level parameter's participation would not guarantee the same level of eNB authenticity.

Two embodiments are disclosed, one utilizing the underlying Internet Protocol Security (IPsec) with improvements and one for direct interactions at eNB level with underlying IPsec in “Manual” mode.

The first embodiment utilizes the underlying Internet Protocol Security eNB-to-eNB communication for LTE and is structured around the standard TCP/IP protocol suite. An understanding of existing internet protocol security and its potential weaknesses is helpful for appreciation of the novelty of this embodiment, and therefore a description thereof follows.

Within TCP/IP protocol, domain protection of IP header information is considered to be critical in preventing the typical attacks which result in address spoofing and which often lead to session hijacking. Network layer authentication and confidentiality are thus employed using a set of Internet Engineering Task Force (IETF) standardized processes called Internet Protocol Security (IPSec). Authentication, which in this context means data integrity and source address protection, is mandatory for IPSec, while confidentiality (encryption) is not.

The three basic components of IPSec are Authentication Protection, Confidentiality Protection, and Security Association. The authentication and confidentiality protection mechanisms are implemented via additional fields in the IP packet. The field for authentication, which is mandatory in IPSec, is the Authentication Header (AH). It is positioned immediately following the IP header. This field contains various subfields that specify the cryptographic algorithms to be used, a sequence number for replay prevention, and integrity hashing referred to as the Integrity Check Value (ICV).

The confidentiality field, which follows the authentication field, is optional and is called the Encapsulating Security Payload (ESP). It contains subfields similar to AH: specification of a unique encryption algorithm, such as DES, AES, 3DES or BLOWFISH, a sequence number subfield, the encrypted payload data, and a subfield containing a hash to integrity protect the encrypted data. The hash employed for ESP protects the integrity of just the encrypted data, whereas the AH hash protects the entire IP packet which, as indicated for IPSec, always includes the AH field and sometimes the ESP field.

To determine whether authentication and confidentiality, as opposed to just authentication, is used, a security association (SA) is set up in IPSec. The SA consists of three parts: a specification of the security algorithms and other parameters, the IP destination address, and an identifier for AH or ESP. The SA is implemented through the Internet Key Exchange (IKE) Protocol, described as follows.

Before any authentication/integrity and confidentiality can be used in IPSec, cryptographic keys, algorithms and parameters have to be negotiated. The IKE protocol contains many protocols for the required negotiation and is used in a variety of scenarios. A simplified view of the IKE protocol is described and related to the present disclosure below.

The initial exchanges between an initiator and a responder establish the initial security association. These exchanges consist of two sets of request/response pairs or a total of four messages.

The first pair establishes cryptographic algorithm usage and performs a Diffie-Hellman exchange to arrive at a seed from which integrity and confidentiality keys are derived. The second pair uses the keys generated from the first exchange to authenticate the first set of messages, swap identities as well as certificates, and provide setup for follow-on child SAs.

The initiator (I) of the protocol sends the following payload:

1. I→R: HDR_(I), SA_(I), g_(I) ^(x), N_(I)

The responder (R) responds with:

2. R→I: HDRR_(R), SA_(R), g_(R) ^(y), N_(R)

This is the first pair of messages of the initial security association. HDR contains header information which primarily maintains the state of the communication between the two entities. SA_(I) and SA_(R) are the security algorithm and parameter negotiation mechanisms, where the initiator proposes the set of choices from which the responder chooses. To process the Diffie-Hellman protocol the values g_(I) ^(x) and g_(R) ^(y) are exchanged to produce the shared secret value g^(xy) which serves as the seed to generate the integrity and confidentiality keys using the prior negotiated algorithms. The quantity g is a generator of the cyclic group F_(p)* (order p-1), where p is a very large prime number. The values p and g are publicly known and all calculations are performed mod p. Lastly, the nonces NR and N_(I) are exchanged to prevent replay.

The second pair of messages is

3. I→R: HDR_(I), SK{ID_(I), Cert_(I), AUTH, SA2_(I), . . . , other fields to create child SAs}

4. R→I: HDR_(R), SK{ID_(R), Cert_(R), Sig_(R), AUTH, SA2_(R), . . . , other fields to create child SAs}

Messages three and four are somewhat simplified from what is specified in the IETF protocol. This second pair employs security key information derived from the first message pair, as stated above. The SK designates a security key operation on the argument shown inside the braces. Two security keys, SK_a (authentication, meaning integrity here) and SK_e (encryption) are generated from g^(xy) (from Diffie-Hellman). They are used to protect the integrity and confidentiality, respectively, of the exchange. The initiator and responder identities (ID_(I) and ID_(R)) and their corresponding identity secrets are proven by each entity to the other; AUTH contains the integrity check values for each direction. The certificates (Cert_(I) and Cert_(R)) provide keying information, apart from SK_a and SK_e, to verify AUTH in both directions.

As long as no eavesdropping of messages 1 and 2 occurs, the SA established between initiator and responder is secure for subsequent child exchanges to take place. However, this initial pair of messages may be vulnerable to a type of the well-known “man-in-the-middle attack” in which an attacker can force each valid entity to use key seeds that it can exploit. The attack described here compromises the entire communication process between initiator and responder, where the attacker is able to masquerade as each one.

A typical man-in-the-middle attack for the initial IKE exchange between I and R is shown in FIG. 6. In steps 1 through 4, A receives g₁ ^(x) from I and g_(R) ^(y) from R; moreover A sends g_(R) ^(m), its Diffie-Hellman value, to I and R, where both assume that the other was the originator of that value instead of the real originator A. Knowing the information that each party has it is easy to show that A shares the Diffie-Hellman seeds g^(mx) and g^(my), respectively, with the valid communicators I and R. A now computes the same encryption (SK_e) and authentication/integrity (SK_a) keys as /using g^(mx) and similarly with R using g^(my).

The SK functions in steps 5 through 8 do not protect either integrity or the confidentiality of the messaging, given that A has spoofed the communications by orchestrating the key usage and successfully masquerading as both I and R. The absence of any pre-shared secret key information prevents the protection of the first two exchanges between I and R. Method and apparatus embodiments for preventing this type of attack are described below.

A first embodiment is shown in FIG. 7, feature 600. At node levels eNBi and eNB₂, (such as the self-configuring eNB and a neighboring eNB, as described above and shown in FIG. 7)) the eNBs share a network distributed secret key K_(s) which is only known by eNB₁ and eNB₂.

With such a node level strong secret, the initial exchange between I (initiator) and R (responder) can be protected by the following pair of messages 600:

1. eNB₁→eNB₂: HDR₁, SA₁, g₁ ^(x), N₁, {HDR₁, SA₁, g₁ ^(x), N₁}K_(s)

2. eNB₂→eNB₁: HDR₂, SA₂, g₂ ^(y), N₂, {HDR₂, SA₂, g₂ ^(y), N₂}K_(s)

The symbols correspond to those defined above. For IPsec messages 1 and 2, the braces notation denotes that message authentication code (MAC) values are added, each representing a hash using the authentication/integrity key, i.e. the shared secret K_(s), of all the components of, respectively, each message. Each hash with K_(s) protects its corresponding IPsec message. If, following the attack shown in FIG. 6, that is, a Man-in-the-middle Attack, the attacker attempts to send g₁ ^(m) to R or g_(R) ^(m) to I, the hash (MAC) in the corresponding message will not agree with that computed by the recipient of the message. As a result, such attempts, or any spoofing attempts, will be detected and defeated. FIG. 7 illustrates this improved IPsec Security Association with respect to the X2C eNB authentication and key association operations.

In a second embodiment indicated at step 630 in FIG. 7 and detailed in FIG. 4, direct eNB authentication is done over the X2C. To guard against possible hijack/replacement or other tampering of surrounding eNBs, a light-weight authentication is disclosed herein to make sure that inter-eNB authentication is assured at the node level. This is opposed to the assumption that the neighboring eNBs are all protected endpoints already, as shown in FIG. 4, between any two pairs of eNBs in LTE.

Referring to FIG. 4, the LTE network prepares a universal shared secret key K and a universal shared eNB credential C for all LTE eNBs for inter-eNB authentication. IN an E-UTRAN parameter response 420, the self-configuring eNBs obtain the parameters over the S1 channel from the network after the eNBs are network authenticated. The LTE also standardizes authentication algorithms Fx and Fy, described further below.

The self-configuring eNB uses the key K and the security algorithm Fx to encrypt the credential C at step 400. The resulting encrypted credential C′ is transmitted in an Auth-Req signal 410 to the neighboring eNB and used by the neighboring eNB to authenticate the self-configuring eNB. The self-configuring eNB also selects a random number (RAND) (step 400) and uses the Fx algorithm to compute an encrypted authentication value X-RES from RAND. Both the C′ and the RAND are transmitted to the neighboring eNB(s) (step 410).

The receiving neighboring eNB(s) then use the shared secret key K and Fx to decode C′ and compare the result with the universal eNB credential C (step 430), which it has in memory. It also uses the received RAND to compute a decrypted authentication value RES using the Fy function. The RES is then sent back in an Auth-Resp signal 440 to the self-configuring eNB to for it to authenticate the neighboring eNB(s) (step 450).

This simplified light-weight inter-eNB authentication avoids the lengthy computations on the SQN, AK, AMF and MAC in the current UMTS UE authentication procedure prior to LTE in order to reduce the security computational load as well as to reduce the signaling message size over X2C.

Returning to FIG. 7, there also may be eNB security key association 630 over X2C. Given that IPsec will be deployed for LTE X2 connections, the use of IPsec and its related IKE-v2 in “Manual” mode with LTE eNB supplied security keys is disclosed with only ciphering performed by IPsec. This ensures the control of X2C security and keys by the LTE via an eNB, ensuring a high security threshold.

For an LTE eNB controlled security key association (for integrity protection and ciphering) the following options are proposed:

First, LTE may standardize an X2C security protection algorithm Fa among all LTE eNBs. The algorithm Fa may be a currently employed algorithm, such as the UMTS f8, or a new algorithm that allows encryption and decryption of information with a shared security key, for example X2C-key.

Second, LTE may standardize a universal set of security keys (which may be chosen for the best security results of the Fa) for the security applications (integrity protection and ciphering) among eNBs over the X2C interface, that is, an indexed set of N keys known to all LTE eNB sites may be defined.

Third, this universal keyset for LTE X2C security operations may be downloaded from the serving aGWs to the self-configuring eNB after the network authentication procedures, such as at the signaling exchange “E-UTRAN Parameter Response” 350. The security key set download to each LTE eNB may occur at the eNB's self configuration stage when the eNB is in the pre-operational mode and thus able to afford the signaling load processing. Existing operational eNBs already have the key set stored.

Fourth, the security key or keys, if there is one for integrity protection and another for deciphering, may be individually chosen or associated between any pairs of two eNBs over an X2C interface, at the self configuration stage, association stage, or at a later operating stage for re-association. In the association stage, only a key index needs to be mutually determined to enable the use of an agreed single security key. This approach benefits the increased security threshold by not sending the root values of the security keys in the message exchange, as in the prior art, reducing computational load by directly deriving the security keys and reducing signaling size in the key agreement message exchange.

Fifth, at the key agreement step, for the same set of the N number of X2 C-Keys, the Diffie-Hellman key indexing method may be used to mutually reach the same key index I such that the security key X2C-key[i] will be used for the intended integrity protection and/or the ciphering operation. This is shown in FIG. 5.

Sixth, the derived security key may be used for both the integrity protection and the ciphering. Alternatively, a different security key may be desired for each operation. In that case one option is to run the same key index exchange procedure separately, in series or parallel, for the other key. An alternative option is to add an offset number to the already obtained key index and then take the modulo N operation again to achieve a new index [0, N-1]. The offset can be obtained by using a number known only to the two sites, for example an identity number such as the self-configuring eNB-Id.

All options (and others within the scope of the invention) can also be run periodically, even when the eNBs are in operational mode, to reselect (re-associate) the security keys. This will reduce the chances of security being broken under long lasting attack attempts.

The inter-eNB authentication and the security key association between the self-configuring eNB and its neighboring eNB(s) can be combined together to achieve both inter-eNB authentication and the security association in one exchange, as shown in FIG. 7, which illustrates overall self-configuring eNB operations over X2C with respect to connected neighboring eNBs.

The inter-eNB operations in FIG. 7 look like a point to point operation, but, from the eNB point of view, it is a point to multi-point operation. Therefore, multicast can be used by the self-configuring eNB if underlying IP layer supports such operation. But each neighboring eNB must respond to the self-configuring eNB individually.

Note that in FIG. 7, the X2C handshake 620 is optional, a described above in reference to FIG. 3. Also, the Alt-1 in the inter-eNB authentication and security key agreement 600 is that described above, where the first two IPsec_Init_SA message are integrity protected. The rest of the IPsec steps can then be carried out as the IPsec normal needs.

If authentication or key exchange fails, with the failure decision being based on several consecutive failed attempts, the self-configuring eNB shall consider the X2C interface invalid and report to the network.

The following E-UTRAN (eNB) parameters may be obtained from the neighboring eNB parameter exchange operation 610: GPS location information; the number of cells the eNB operates and the cell-Id(s); service operator's identity or home PLMN Id; eNB measurement or measurement group/association information; radio parameters for the Cell(s), such as frequency band and center-frequency, cell transmit bandwidth value, power control information, baseline cell common channel configurations, Multiple Input Multiple Output (MIMO) and directional antenna information, Multimedia Broadcast Multicast Service (MBMS) over a Single Frequency Network (MBMS SFN) information, and MBMS resource information; and service parameters for the Cell(s), such as MBMS information, location services (LCS) information, and common system information (SI) information shared among eNBs.

Although the features and elements disclosed are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements of the present disclosure. The methods or flow charts provided may be implemented in a computer program, software, or firmware tangibly embodied in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.

A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) module. 

1. An evolved NodeB (eNodeB) comprising: a processor configured in response to the eNodeB being initially powered on to initiate a self configuration process; wherein the processor is further configured in the self configuration process to authenticate with a network, to request configuration parameters from the network and in response to the request for configuration parameters, to receive a response including configuration parameters; wherein the processor is further configured to send another eNodeB a request for second parameters and in response to the request for second parameters, to receive a response including the second parameters.
 2. The eNodeB of claim 1 wherein the processor establishes an S1 interface with the network and the request for the configuration parameters and the response to the request for configuration parameters are transferred using the S1 interface.
 3. The eNodeB of claim 1 wherein the processor establishes the S1 interface using an Internet Protocol (IP) address.
 4. The eNodeB of claim 1 wherein the response including the second parameters includes an indication of cells operated by the another eNodeB.
 5. The eNodeB of claim 4 wherein the response including the second parameters further includes MBMS SFN information from the another eNodeB.
 6. The eNodeB of claim 1 wherein the processor is further configured to initiate a self optimization procedure.
 7. An method for self configuration by an evolved NodeB (eNodeB) comprising: in response to the eNodeB being initially powered on, initiating a self configuration process by the eNodeB; authenticating the eNodeB with a network; requesting by the eNodeB configuration parameters from the network; in response to the request for configuration parameters, receiving by the eNodeB a response including configuration parameters; sending by the eNodeB another eNodeB a request for second parameters; and in response to the request for second parameters, receiving by the eNodeB a response including the second parameters.
 8. The method of claim 7 further comprising establishing an S1 interface with the network and the request for the configuration parameters and the response to the request for configuration parameters are transferred using the S1 interface.
 9. The method of claim 7 wherein the S1 interface is established using an Internet Protocol (IP) address.
 10. The method of claim 7 wherein the response including the second parameters includes an indication of cells operated by the another eNodeB.
 11. The method of claim 10 wherein the response including the second parameters further includes MBMS SFN information from the another eNodeB.
 12. The method of claim 7 further comprising initiating by the eNodeB a self optimization procedure. 